home *** CD-ROM | disk | FTP | other *** search
Text File | 1990-06-08 | 2.0 KB | 52 lines | [TEXT/GEOL] |
- Item 4507960 4-June-90 13:23PDT
-
- From: GARDNER.P Gardner, Preston
-
- To: V0683 Amoco Tech, Eric Berdahl,VAR
- MACAPP.TECH$ MacApp Technical
-
- Sub: re> CPlusLoad/NeedsFPU in MAB
-
- re CPlusLoad/NeedsFPU in MABuild
-
- This is a result of CPlus and MacApp confusing each other needlessly.
-
- The original intention with load and dump was to insure that the floating point
- options -elems881 and -mc68881 are compatible between the load and the dump.
- In the version you have this is done by reading these options from the load
- file and ignoring what's on the command line when you do the load. Or rather,
- the options are not ignored, the compiler gives an error if you use them on the
- load.
-
- This is too confusing, so we have changed the rules in 3.1 final to require
- instead that if you have either of these options on the command line when you
- do the dump, you have to also have them on the load line.
-
- Example:
-
- Old way:
- CPlus -dump headers.dump -mc68881 headers.cp
- CPlus -load headers.dump myprog.cp # leave -mc68881 out
-
- New way:
- CPlus -dump headers.dump -mc68881 headers.cp
- CPlus -load headers.dump -mc68881 myprog.cp # options must match
-
- Not all the options have to match in the dump and load -- only the FP ones and
- -sym care about this. The compiler will issue a warning if they don't match.
-
-
- My theory is that the MacApp people saw the way this worked and assumed that
- CPlus won't let you use floating point if you do a load.
-
-
- For MABuild, I'm not sure what you do to get around this. Try making the dump
- file with -NeedsFPU and then just don't bother to use -NeedsFPU when you do the
- load. It will be in there, don't worry. (Except that the Link line will have
- to be fixed to find the 881 libraries, I think...) It takes a MacApp person to
- answer this part.
-
- In the future this won't happen. It is fixed in 3.1 final (to be released in a
- few weeks) but I don't know what version of MacApp will have this fixed.
-
-